swan-cern: Add swan-cern-system chart for system components #258
+227
−137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
etejedor
previously approved these changes
Aug 28, 2024
PMax5
force-pushed
the
feature/decouple-charts
branch
from
59576cf to
d613964
Compare
This option ensures that chart resources are not deployed unless declared in the values. It was introduced following the goal to adopt a blue/green strategy when promoting new features in SWAN. The resources in one of the environments will be allocated temporarily while a feature is being tested and will then be removed by toggling this chart flag.
PMax5
force-pushed
the
feature/decouple-charts
branch
2 times, most recently
from
819068e to
13aebfc
Compare
PMax5
changed the title
PMax5
force-pushed
the
feature/decouple-charts
branch
3 times, most recently
from
1940f17 to
e3207b1
Compare
This way, gpu-operator and fluentd can belong to a new chart and be deployed independently of the swan-cern chart. The swan-cern chart will then be able to be deployed twice in the same cluster, in two namespaces, since all the remaining components can be duplicated and coexist in the same cluster (e.g. eos, cvmfs).
PMax5
force-pushed
the
feature/decouple-charts
branch
from
e3207b1 to
3d52e2f
Compare
This is to bump the chart version automatically, through the CI, everytime there are changes.
The monitoring charts will be responsible for deploying prometheus and fluenbit, to push the service metrics and logs to the instances of monit at CERN. These deployments will replace the prometheus deployed by the cern-magnum chart on cluster creation and the current fluentd that is deployed with the swan-cern-system chart. For now, only the metrics deployments will be enabled, as we have not migrated from fluentd to fluentbit in regards to the logs.
PMax5
force-pushed
the
feature/decouple-charts
branch
from
3d52e2f to
1ca8ae2
Compare
etejedor
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This option ensures that chart resources are not deployed unless declared in the values. It was introduced following the goal to adopt a blue/green strategy when promoting new features in SWAN.
The resources in one of the environments will be allocated temporarily while a feature is being tested and will then be removed by toggling this chart flag.